Languguage OS 2/Languguage OS II Version 10-94 (Knowledge Media)(1994).ISO/language/embedded/embedded/readme_r.03

Text File | 1994-10-20 | 6KB | 125 lines

This is taken from the file INSTALL.

==============================================================
October 11, 1994

This is an alpha release of RTEMS.  It is an alpha release because
the following tasks must be completed before a full release occurs:

    + Ada implementation updated
    + documentation is not updated

This release only has the source code for the C implementation.
The C implementation has been fully tested on the three reference
processors (m68020, i386, and i960ca).  If you are interested in
using the C implementation of RTEMS, I urge you to use this one.
We have made it significantly easier to build.  It is now possible
to edit a host configuration file, set a few environment variables,
type "gmake install" and PRESTO! RTEMS is built.  It was much more
difficult to do this with 3.1.0 and if you had problems I apologize
and ask you to give this alpha release a try.  I talked a few people
through the process on 3.1.0 and hope I don't have to ever again.
I have new found respect for technical support personnel. :)

If you want to port RTEMS to a new CPU or HOST, PLEASE use this
release.  It will make your life much easier.

The changes to the source code itself were minor with one exception.
Timer service routines (aka watchdog timer functions) now take an argument.
This argument is a "void *" and is passed to the timer_fire_after and
timer_fire_when directives.

The execution times are basically the same as with Release 3.1.0.

Documentation issues:

1. Accuracy of 3.1.0 Release and Installation Notes is questionable.

2. C User's Guide: timer_fire_after and timer_fire_when now take
   an extra argument which is a "void *" to be passed to the
   timer service routine when it fires.

Here is a crude first cut at installation instructions.  The file
c/make/README provides more info on the makefile structure.  If
you have trouble try email to one of the addresses below my signature.
You should be able to configure and build RTEMS with the following steps:

1. untar the file.

2. If you are a Modules user:
      a. use one of the modulefiles in c/Modules/rtems as a starting
         point and make one for your system.  You may call this
         modulefile anything you want, we will refer to it as
         LOCAL_RTEMS_MODULE in the instructions.
      b. execute the command "module use RTEMS_MODULE_DIR" where
         RTEMS_MODULE_DIR is the full path of c/Modules/rtems.
      c. module load YOUR_RTEMS_MODULE.

   If you are not a modules user (well consider using it :) ), you
   will have to make some changes to your environment varables by
   hand or by "sourcing" a file with the appropriate commands for your
   shell.  The modules files are still a good place to look.  Here are
   the changes which must be made:
      a. set RTEMS_BSP to the name of your target (for example,
         mvme136 or force386).
      b. set RTEMS_ROOT to the full path of the "c" directory.
      c. set RTEMS_GNUTOOLS to the full path for the cross development
         tools.
      d. set RTEMS_HOST to the type of host you have.  NOTE: Even if
         you see a host which matches look to see if everything points
         to the right place.  GNU tools are used and these files point to
         the correct place for them for whomever submitted the host
         configuration file (c/make/os/${RTEMS_HOST}.cfg).
      e. set RTEMS_CUSTOM to the name of the make customization file
         you will use.  Typically, this file is:
           ${RTEMS_ROOT}/make/custom/${RTEMS_BSP}.cfg
         This file defines the make rules for the toolset used with the
         target.
      f. insure ${RTEMS_GNUTOOLS}/bin is in your PATH

3.  Verify that the make host configuration file (c/make/os/${RTEMS_HOST}.cfg).
    is correct for your system.  GNU tools are used and these files point to
    the correct place for them for whomever submitted the host configuration.
    It is especially important that these variables be set correctly.

4.  If you are using GNU tools and a supported CPU and target,
    c/make/custom/${RTEMS_BSP}.cfg should be fine for you.  If you are
    using GNU tools, a supported CPU, and a new target, copy it as a
    starting point.  We have found that each target requires something
    special such as massaging Srecords in some unique way.

5.  cd ${RTEMS_ROOT}/c

6.  gmake env            -- installs environment

7.  gmake install        -- compiles and installs RTEMS

    RTEMS should automagically compile and install itself.  Install point
    is based on the PROJECT_RELEASE variable in c/make/main.cfg.  It is
    possible to install into the default location (c/${RTEMS_BSP}) and
    copy this to another location.  This directory contains an entire binary
    release of RTEMS including test executables for the target.

The directory structure is different from 3.1.0.  The number of directories
has been REDUCED!!!  The new structure should feel more familiar to
users of GNU packages.

As with the previous release, the directory structure supports simultaneous
work on different cpu and target combinations.

Please don't be scared off.  This release IS easier to build than the
previous one and if we get constructive criticism we will try to make
it even easier.

Finally, if you use RTEMS let us know.  The success of this project
is largely measured by how many users we have.  Similarly, if you
decide not to use RTEMS, let us know why.  We are open to good
suggestions.

Thanks.  If you have trouble try email to one of the addresses below
my signature.

Joel Sherrill
[e-mail]
[e-mail]